Extended data collection for multi-merchant purchasing environment for downloadable products

ABSTRACT

A multi-merchant purchasing system is configured to identify downloadable products selected by a user for purchase. The identified downloadable products are offered by multiple merchants. The multi-merchant purchasing system enables the user to purchase all of the downloadable products in a single transaction. Specifically, the multi-merchant purchasing system determines payment information associated with the user and, with minimum user-interaction, sends the payment information to applications associated with the merchants for processing. The multi-merchant purchasing system may also be configured to receive purchase information from the merchant applications and maintains the purchase information for the user in a locker. The multi-merchant purchasing system may further be configured to automatically download and install the purchased product onto the user&#39;s computing device through a software assistant. To ensure privacy and security, the multi-merchant purchasing system may include a credit card quarantine module to secure credit card data by encoding and multiple levels of encryptions. The multi-merchant purchasing system may be further configured to accept a request to collect extended user data related to the user on behalf of merchants and return the collected extended user data to the merchants.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation-in-part application of U.S. patent application Ser. No. 11/042,932, filed Jan. 24, 2005.

This application is related to the following U.S. patent applications, filed on the same date as this application, and the content of which is hereby incorporated by reference.

-   -   U.S. patent application, Ser. No. 11/042,916, titled         “MULTI-MERCHANT PURCHASING ENVIRONMENT FOR DOWNLOADABLE         PRODUCTS”.     -   U.S. patent application, Ser. No. 11/042,769, titled “SOFTWARE         ASSISTANT FOR MULTI-MERCHANT PURCHASING ENVIRONMENT FOR         DOWNLOADABLE PRODUCTS”.     -   U.S. patent application, Ser. No. 11/042,305, titled “PAYMENT         INFORMATION SECURITY FOR MULTI-MERCHANT PURCHASING ENVIRONMENT         FOR DOWNLOADABLE PRODUCTS”.

BACKGROUND

As more and more businesses invest in online commerce infrastructure, purchasing products on the Internet continues to gain popularity among consumers. Shopping online has many advantages. For example, one advantage is that a consumer can browse, research and purchase products in an efficient manner without expending the time and effort of visiting physical stores. Another advantage is that online stores do not have the limitation of retail space and tend to have a better selection of products than physical stores.

One popular way for consumers to shop online is to visit an online equivalent of a department store. While an online department store may offer a variety of different products, the store often carries only products that are deemed to be profitable relative to business constraints, such as inventory, profit margins, etc. Consequently, the selection of products in any particular area may be limited. Also, an online department store may not be able to offer the best price for all of the products that it carries. Thus, if a consumer wants to purchase a particular product and at the best price, the consumer may have to visit multiple online department stores and specialty stores, which can be a time-consuming process.

To provide a better online shopping experience for consumers, many shopping services enable consumers to compare prices on products available on the Internet. These shopping services typically allow a consumer to search for a particular product that is offered by multiple stores and provide prices of the products at each store for comparison. In the comparison page, the price for each store is generally followed by a link to the store. A consumer may follow the link to visit the selected store and purchase the product. Although shopping services provide more selection and better prices for products, purchasing multiple products in this manner often involves substantial effort and is time-consuming. In particular, a consumer typically has to go through multiple purchasing processes.

An efficient way for consumers to purchase products from multiple merchants continues to elude those skilled in the art.

DESCRIPTION OF THE DRAWINGS

These and other features and advantages of the present invention will be better understood from the following detailed description read in light of the accompanying drawings, wherein:

FIG. 1 shows an example multi-merchant purchasing system and related components.

FIG. 2 illustrates example communications associated with purchasing downloadable products with the multi-merchant purchasing system shown in FIG. 1.

FIG. 3 illustrates example communications associated with downloading products that are purchased through the multi-merchant purchasing system 100 shown in FIG. 1.

FIG. 4 illustrates another set of example communications associated with downloading purchased products.

FIG. 5 illustrates example communications for securely sending credit card numbers from a credit card quarantine module to a merchant service.

FIG. 6 shows example data that may be handled by the multi-merchant purchasing system shown in FIG. 1.

FIG. 7 shows example data that may be handled by the credit card quarantine module in FIG. 1.

FIG. 8 shows an example process for enabling a user to make a purchase in a multi-merchant purchasing environment.

FIG. 9 shows an example process for enabling a user to download products that are properly purchased.

FIG. 10 shows an example process for downloading a downloadable product purchased through a multi-merchant purchasing system.

FIG. 11 shows an example process for downloading and installing downloadable product purchased through a multi-merchant purchasing system.

FIG. 12 shows an example process for securely providing payment information to a merchant for purchasing downloadable products through a multi-merchant purchasing system.

FIG. 13 is a screenshot of an example user interface provided by a catalog provider for purchasing downloadable products from multiple merchants.

FIG. 14 is a screenshot of an example user interface for purchasing downloadable products through a multi-merchant purchasing system.

FIG. 15 is a screenshot of an example user interface for managing downloadable products newly purchased through a multi-merchant purchasing system.

FIG. 16 is a screenshot of an example user interface provided by a software assistant for downloading and installing products purchased through a multi-merchant purchasing system.

FIG. 17 is a screenshot of an example user interface provided by a locker of a multi-merchant purchasing system.

FIG. 18 is an example screenshot of a user interface provided by a multi-merchant purchasing system for a user to review purchases made with the system.

FIG. 19 is an example screenshot of a user interface provided by a multi-merchant purchasing system for a user to manage an account on the system.

FIG. 20 shows example extended user data that may be sent by a merchant to the purchasing module in FIG. 1.

FIG. 21 shows an exemplary computer device for implementing the described systems and methods.

DETAILED DESCRIPTION

The systems, methods, and data structure described herein relates to an environment for purchasing items from multiple merchants. A multi-merchant purchasing system is configured to identify downloadable products selected by a user for purchase. The identified downloadable products are offered by multiple merchants. Typically, the user would have to make separate purchases with each of merchants and go through multiple purchasing processes. The multi-merchant purchasing system enables the user to purchase all of the downloadable products in a single transaction. Specifically, the multi-merchant purchasing system determines payment information associated with the user and, with minimum user-interaction, sends the payment information to applications associated with the merchants for processing. The multi-merchant purchasing system may also be configured to receive purchase information from the merchant applications and maintains the purchase information for the user in a locker. The multi-merchant purchasing system may further be configured to automatically download and install the purchased product onto the user's computing device through a software assistant. To ensure privacy and security, the multi-merchant purchasing system may include a credit card quarantine module to secure credit card data by encoding and multiple levels of encryptions. These and other aspects of the multi-merchant purchasing system will be discussed below in detail.

FIG. 1 shows an example multi-merchant purchasing system 100 and related components. Multi-merchant purchasing system 100 provides a centralized experience for a user/consumer to purchase, download, and manage products from multiple merchants. Multi-merchant purchasing system 100 may interact with multiple catalog providers, such as catalog provider 150, and to manage the purchasing aspects of a user's online shopping experience. Multi-merchant purchasing system 100 may also interact with merchant services 131-133 to obtain updated product information from merchants and to provide payment information to the merchants. Multi-merchant purchasing system 100 may further interact with merchant services 131-133 to receive a request for a set of extended data that the multi-merchant purchasing system 100 may collect from the user/consumer at the time of purchase. Multi-merchant purchasing system 100 may interact with a user authentication system 120 to authenticate users before providing services. Multi-merchant purchasing system 100 may further interact with a software assistant 140 to provide content of purchased products for downloading and installation onto a user's device.

Catalog provider 150 is configured to provide an online shopping environment for users from which to select products. Catalog provider 150 typically includes a website that offers information about products from multiple merchants. Catalog provider 150 may be configured to interact with merchant services 131-133 to acquire and update information about the products.

Catalog provider 150 may be configured to enable a user to select products from different merchants for purchasing with a shopping cart utility. The utility may include a list of the selected products and some basic information about the products, such as the merchants that offer the products, the product serial numbers, or the like. When the user chooses to purchase the selected products, catalog provider 150 may be configured to provide information of the shopping cart utility to multi-merchant purchasing system 100, which handles the purchasing process. Although only catalog provider 150 is shown in FIG. 1, it is to be appreciated that multi-merchant purchasing system 100 may be configured to handle purchases from multiple catalog providers.

For ease of discussion, multi-merchant purchasing system 100 is illustrated as logical components and modules. As shown in FIG. 1, multi-merchant purchasing system 100 may include purchasing module 103, locker module 105, credit card quarantine module 111, administration modules 109, and purchasing information data store 107.

Purchasing module 103 is configured to handle the purchasing aspects of the functionalities provided by multi-merchant purchasing system 100. Purchasing module 103 presents a user-interface for a user to purchase downloadable products from multiple merchants with a single transaction. Particularly, purchasing module 103 enables a user to purchase downloadable products from multiple merchants by going through the purchasing process only once. For example, multi-merchant purchasing system 100 enables the user to purchase products from each of the merchants corresponding to merchant services 131-133 by presenting the purchases to the user as a single transaction.

Purchasing module 103 is configured to receive from other services, such as catalog provider 150, shopping cart information that identifies downloadable products to be purchased by a user. Purchasing module 103 may interact with user authentication system 120 to authenticate the user prior to the purchasing process. The shopping cart information typically includes a list of the selected products to be purchased, the merchants that offer the products, serial numbers, availability, prices, or other basic information about the products.

Catalog provider 150 typically allows merchant services 131-133 to provide product information in a periodic basis. Thus, depending on timing, the shopping cart information provided by catalog provider 150 to purchasing module 103 may not be up to date. If necessary, purchasing module 103 is configured to interact with merchant services 131-133 to obtain updated certain information about the product, such as availability, pricing, or the like. Extended data collection module 108 may be configured to receive a request for a set of extended user data from merchant services 131-133. Such extended user data may be related to user information necessary for use by the merchant services 131-133 to key a software license, to request permission to email a company newsletter, or the like. Further, such information may be configured as a portion of extensible markup language (XML).

To perform the purchasing process, purchasing module 103 typically prompts the user to provide transactional information related to purchasing the downloadable products, such as personal information, shipping information, payment information, extended user data, or the like. Multi-merchant purchasing system 100 typically does not handle payment transactions. Purchasing module 103 is configured to provide the transactional information to merchant services 131-133 for purchasing downloadable products from each of the merchants. Before allowing the user to provide the transactional information, multi-merchant purchasing system 100 is configured to alert the user that the provided information will be sent to the merchants for processing. Purchasing module may also be configured to record the transactional information for the user and apply the information for subsequent purchases without asking to user to provide the information again.

Upon receiving credit card payment information from the user, purchasing module 103 may be configured to safeguard the credit card number by immediately sending the number to credit card quarantine module 111. To ensure security, purchasing module 103 may also be configured to immediately delete any records of the credit card number. Purchasing module 103 is configured to receive a token from credit card quarantine module 111 to represent the credit card number. The token may be stored along with other credit card information for the user in purchasing information data store 107. To provide payment information of the user to a merchant, purchasing module 103 is configured to send the token to credit card quarantine module 111 along an identifier of the merchant. In response, purchasing module 103 receives from credit card quarantine module 111 a credit card number that is encrypted with a public key associated with the merchant to which the number will be forwarded. Purchasing module 103 is configured to provide the encrypted credit card number to the merchant service associated with the merchant along with other transactional information.

After a payment transaction has been completed by a merchant service for the purchase of a downloadable product, purchasing module 103 is configured to receive purchasing information related to the purchased product from the merchant service. Purchasing information may include license information of the product, key to activate the product, warranty, support, extended user data, or the like. Purchase module 103 is configured to store the purchasing information in the purchasing information data store 107. Extended data collection module 108 may further store all or portions of extended user data in the purchasing information data store 107.

Locker module 105 enables users to manage and access downloadable products purchased through multi-merchant purchasing system 100. Locker module 105 is configured to interact with purchasing information data store 107 to retrieve purchasing information associated with the users. Locker module 105 may provide various types of information about purchased products to the users, such as license information of the products, purchase history, estimated downloading time for the products, warranty information, or the like.

Locker module 105 is configured to interact with software assistant 140 to enable a user to download a newly purchased product. Subsequent to the initial downloading, depending on the license acquired, locker module 105 may enable the user to perform other processes related to the downloadable product, such as repeated downloading of the product, downloading the product onto another computer, or the like. In one embodiment, locker module 105 retains information of all purchased products associated with a user's computing device. Locker module 105 may enable to the user to automatically download and install the purchased products onto the computer device through software assistant 140. Locker module 105 is configured to enable software assistant 140 to download products from a link provided by merchant services 131-133, but is not typically configured to provide the content of the downloadable product directly to software assistant 140.

Credit card quarantine module 111 is configured to store and safeguard credit card numbers for multi-merchant purchasing system 100. Credit card quarantine module 111 may be implemented as a part of the multi-merchant purchasing system 100 or as a separate component. Credit card quarantine module 111 is configured to receive credit card number from purchasing module 103 and to prevent the number from being sent out without encryption. Credit card quarantine module 111 is configured to generate tokens for each received credit card number and to associate each number with the corresponding token. The tokens are provided to purchasing module 103 for storing with other information associated with the user and a particular transaction. Credit card quarantine module 111 may also determine public/private key pairs where each pair of keys corresponds to each merchant associated with multi-merchant purchasing system 100. Credit card quarantine module 111 is configured to provide each private key to the corresponding merchant and to encrypt credit card numbers with the corresponding public key before sending the numbers to the merchant.

Purchase information data store 107 typically includes purchase information associated with transactions for each user. Purchase information data store 107 may further include default values for extended user data. Purchase information data store 107 may be implemented as a database system for use by components of multi-merchant purchasing system 100. For example, purchase information data store 107 may be implemented as a Structured Query Language (SQL) database system. Administrative module 109 is configured to allow a system administrator to maintain multi-merchant purchasing system 100. For example, administrative module 109 may enable a system administrator to manage purchasing information data store 107.

User authentication system 120 is configured to enable a user to be authenticated prior to purchasing downloadable products on multi-merchant purchasing system 100. Any type of user authentication system may be used. For example, user authentication system 120 may include a MICROSOFT® PASSPORT system.

Software assistant 140 is configured to enable a user to download products purchased on multi-merchant purchasing system 100. Software assistant 140 is typically implemented as an application on a user's computing device. Software assistant 140 interacts with locker module 105 to determine which downloadable products are available for downloading and the locations at which the products can be downloaded. Software assistant 140 is configured to download the products at the determined locations, which are typically maintained by merchant services 131-133. Software assistant 140 is also configured to calculate a hash of a downloaded product for authentication purposes. For example, the hash may be compared with another hash determined by the merchant service that provided the product to determine whether the downloaded product is valid. The downloaded product may be invalid due to a variety of reasons, such as data corruption, substitution, hacking, or the like. The comparison may be performed by software assistant 140 or multi-merchant purchasing system 100.

Software assistant 140 is also configured to install downloaded products into the user's computing device. In one embodiment, software assistant 140 is configured to interact with locker module 105 to automatically download and install the purchased products associated with a computer device. In this manner, the computer device may be automatically imaged with the purchased products with minimum effort by the user.

Merchant services 131-133 are configured to receive transactional information from multi-merchant purchasing system 100 and to perform operations related to purchasing of downloadable products offered by the merchants. Merchant services 131-133 may be configured to provide any type of downloadable products, such as software, music, videos, graphics, or other type of digital content. The merchants corresponding to merchant services 131-133 may include any type of entities, such as producers of the downloadable products, online retailers, resellers, or the like. In particular, merchant service 131-133 may also be configured to serve as catalog providers.

Each of the merchant services 131-133 is configured to use payment information received form multi-merchant purchasing system 100 to arrange for payment for the downloadable products. In particular, each of the merchant services 131-133 is configured to receive from multi-merchant purchasing system 100 encrypted credit card numbers to process payments. Each of the merchant services 131-133 processes a private key provided by multi-merchant purchasing system 100 to decrypt the credit card numbers that are encrypted by credit card quarantine module 111.

After receiving payment, merchant services 131-133 are configured to provide multi-merchant purchasing system 100 with purchasing information, such as software licenses, receipt, shipping tracking number, downloading location, activation keys, or the like. Merchant services 131-133 may be configured to make the product available to the user for downloading in any manner, such as through downloading manager 140. Merchant services 131-133 may be configured to provide a hash value of the downloaded product for verification.

Catalog providers 150, merchant services 131-133, modules of multi-merchant purchasing system 100, software assistant 140 and user authentication system 120 may be implemented as any type of applications, such as web services. The term “web service” or “application service” means an application that is capable of interacting with other applications through one or more protocols, such as network protocols. Typically, web services are configured to send data to and receive data from applications through any type of networks. A web service may be identified by an identifier, such as an Internet Protocol (IP) address or a Uniform Resource Locator (URL), so that other applications can readily locate and communicate with the web service.

Web services may also be configured to facilitate communication between applications that are executing on difference types of devices and operating environments. Web services may communicate with other applications using various universal standards. For example, web services may use Extensible Markup Language (XML) to tag data, Simple Object Access Protocol (SOAP) to transfer the data, Web Services Description Language (WSDL) to describe the services available, or Universal Description, Discovery and Integration (UDDI) to list what services are available. The web services may be implemented in any type of software code, such as XML.

FIG. 2 illustrates example communications associated with purchasing downloadable products with multi-merchant purchasing system 100 shown in FIG. 1. For the purpose of discussion, a user has selected downloadable products through catalog provider 150 from a number of merchants, which include the merchant that corresponds to merchant service 131.

When the user chooses to purchase the downloadable products in the shopping cart, catalog provider 150 may send message 202 to multi-merchant purchasing system that includes the shopping cart information. The shopping cart information may include information about the products, such as serial numbers, the merchants associated with the products, description, prices, or the like. In response, multi-merchant purchasing system 100 may send message 204 to client 201 associated with the user that includes a request for user authentication. Multi-merchant purchasing system 100 may perform user authentication with client 201 or another computing device that includes a user authentication system. In response, client 201 (or the other computing device) may send message 206 that includes authentication information of the user.

Multi-merchant purchasing system 100 may send message 208 that includes a request for product information to merchant service 131. Message 208 may further include a request for a set of extended user data that the multi-merchant purchasing system 100 may collect from the client 201 on behalf of the merchant service 131. Message 208 may be sent if the product information determined by multi-merchant purchasing system 100 is not valid or has expired. Message 208 may be sent to request the set of extended user data that the multi-merchant purchasing system 100 may collect from the client 310 on behalf of the merchant service 131. In response, merchant service 131 may send message 212 that includes updated product information and extended user data to be collected by the multi-merchant purchasing system 100. Multi-merchant purchasing system 100 may present the information to the user prior to finalizing the purchase. Multi-merchant purchasing system 100 may further present a user interface to the client 310 to collected extended user data on behalf of the merchant service 131. Such a user interface may be created by enumerating the extended data request and determining the name of the extended data to be collected and providing an input for the user to enter the value of the extended data.

Multi-merchant purchasing system 100 may send message 214 to the client to request for payment. In response, client 201 may send message 216 that includes transactional information and any extended user data that was collected. The transactional information may include payment information, such as a credit card number, expiration date, security code, name, home address, phone number, or the like. The extended user data may include information necessary to key a software license, permission to send a user a company newsletter email, or the like. The transactional information may also include other purchase-related information, such as shipping address, instructions, or the like. Message 216 may not be necessary if the multi-merchant purchasing system 100 has such transactional information from prior interaction with the user and is authorized to provide such information to merchants. Further, message 216 may not be necessary if the multi-merchant purchasing system 100 has stored default values for the extended user data that may have been collected in an earlier transaction or at any other time. Multi-merchant purchasing system 100 may send message 218 that includes transactional information and any collected and/or default extended user data to merchant service 131. After performing payment related transactions, merchant service 131 may send message 220 that includes a receipt and purchase information associated with the purchased products. For example, the purchase information may include licensing information, warranty information, shipping information, downloading location, or the like.

For illustrative purposes, only communications with a single merchant are shown for this purchase. It is to be appreciated that the purchase may include downloadable products from multiple merchants and communications with these merchants may be performed similar to those illustrated in FIG. 2.

FIG. 3 illustrates example communications associated with downloading products that are purchased through multi-merchant purchasing system 100 shown in FIG. 1. A user may employ a software assistant 140 to obtain the downloadable products. Software assistant 140 may send message 302 that includes a request for downloading purchased products to multi-merchant purchasing system 100. In response, multi-merchant purchasing system 100 may send message 304 that includes a request for downloading location to merchant service 131.

Merchant service 131 may send message 306 that includes a downloading location for the purchased products and a hash value associated with the products. The location may include an address, such as a Universal Resource Locator (URL), an Internet Protocol (IP) address, or the like. Multi-merchant purchasing system 100 may send message 308 with the downloading location and the hash value to software assistant 140. Software assistant 140 may send message 310 that includes a request to initiate downloading. In response, merchant service 312 may provide the product content in message 312.

After receiving the product content, software assistant 140 may calculate a hash value from the content and compare the calculated hash value with the value received in message 308. If the hash values do not match, the received content would be determined to have been compromised and would be invalidated. The communications in FIG. 3 show that software assistant 140 is configured to compare the hash values. It is to be appreciated that the software assistant 140 may also be configured to provide the calculated hash to multi-merchant purchasing system 100 for comparison.

FIG. 4 illustrates another set of example communications associated with downloading purchased products. The example communications shown in FIG. 4 are somewhat similar to the example communication shown in FIG. 3. The differences in the communications account for the fact that merchant service 131 does not provide the hash value at the time the downloading location is provided.

As shown in FIG. 4, software assistant 140 may send message 402 that includes a request for downloading purchased products to multi-merchant purchasing system 100. In response, multi-merchant purchasing system 100 may send message 404 that includes a request for downloading location to merchant service 131.

Merchant service 131 may send message 406 that includes a downloading location for the purchased products. Multi-merchant purchasing system 100 may send message 408 with the downloading location to software assistant 140. Software assistant 140 may send message 410 that includes a request to initiate downloading. In response, merchant service 412 may provide the product content in message 412.

After providing the product content to software assistant 140, merchant service 131 may send message 414 that includes a hash value associated with the product content to multi-merchant purchasing system 100. Software assistant 140 may calculate a hash value from the product content received in message 412 and send message 416 that includes the calculated hash value and a request for validation to multi-merchant purchasing system 100. Multi-merchant purchasing system 100 may compare the hash values received in message 414 and message 416. If the hash values match, multi-merchant purchasing system 100 may send message 418 that includes a validation confirmation to software assistant 140.

The communications in FIG. 4 show that multi-merchant purchasing system 100 is configured to compare the hash values. It is to be appreciated that multi-merchant purchasing system 100 may also be configured to provide the hash value received in message 414 to software assistant 140 for comparison.

FIG. 5 illustrates example communications for securely sending credit card numbers from credit card quarantine module 111 to merchant service 131. To prepare for secured transfer of credit card numbers, credit card quarantine module 111 and merchant service 131 may establish a public/private key arrangement so that communications between quarantine module 111 and merchant service 131 may be encrypted.

When the purchasing module 103 receives credit card data, such as a credit card number and related information, purchasing module 103 sends message 506 to credit card quarantine module 111 with the credit card data. In response, the credit card quarantine module 111 may return a token to represent the credit card data to purchasing module 103 with message 508.

When the purchasing module 103 determines to send the credit card data to merchant service 131, the purchasing module 103 may send message 510 that includes a request for credit card data along with the identity of the merchant to which the data will be sent and the token corresponding to the credit card data. In response, credit card quarantine module 111 may send message 512 that includes the requested credit card data encrypted with a public key corresponding to the merchant. Purchasing module 103 may send message 514 that includes the encrypted credit card data to merchant service 131. The merchant service may decrypt the credit card data using the corresponding private key.

The example communications in FIG. 2-5 may be structured in any manner, such as encoded as web service communications. To enhance security, the example communications may also be encrypted using any encryption algorithms and methods. Thus, the content of the messages, such as credit card data, may be secured with multiple levels of encryption.

FIG. 6 shows example data that may be handled by multi-merchant purchasing system 100 shown in FIG. 1. The example data in FIG. 6 is shown to be included in purchased information data store 107. The example data may also be included in any data structure and communications between multi-merchant purchasing system 100 and other components, such as merchant services 131-133 and software assistant 140 shown in FIG. 1.

As shown in FIG. 6, purchasing information data store 107 may include user identifiers 602, user information 603, purchase records 604, merchant information 605, production information 606, license information 608, downloading records 610, configuration data 612, and extended user data 614.

User identifiers 602 identify users that are associated with multi-merchant purchasing system 100. User identifiers 602 may serve as an indexing field for structuring other data in the data store 107. User information 603 includes information about each user identified by user identifiers 602. User information 603 may include personal information, such as name, address and phone number, payment information, or the like.

Purchase records 604 include records of purchases made by the users indicated by user identifiers 602. Each entry of the purchase records 604 may include a transaction number, date and time, a list of products, prices, or the like. Purchase records 604 may serve as an indexing field for structuring other data related to purchases. Merchant information 605 may include information about the merchant from which downloadable products were purchased in a particular transaction indicated in purchase records 604. Product information 606 may include detail information about the purchased products. License information 608 includes data about the licenses of the purchased products. For example, license information may include license numbers, keys, descriptions, restrictions, or the like. Downloading records 610 may include records of downloading event for products of each purchase. Configuration data 612 may include configurations of purchased products for a computing device associated with each user indicated in user identifiers 602. Configuration data 612 may be used to automatically image a user's computing device with downloadable products purchased through multi-merchant purchasing system 100.

Extended user data 614 may include a set of default information that may have been collected from a user at an earlier time. The extended user data 614 may include information related to the user's organization, the user's preferences with regard to receive marketing information, and the like. Extended user data 614 may include information related to a specific transaction and therefore it may not be necessary to store a part of or all of the extended user data that was collected as part of a specific transaction.

FIG. 7 shows example data that may be handled by credit card quarantine module 111 in FIG. 1. As shown in FIG. 7, the example data may be included in credit card quarantine data store 700. The example data may include credit card numbers 702, tokens 704, merchant identifiers 706 and public keys 708. Tokens 704 are associated with credit card numbers 702. Each of the tokens 704 may be provided to another component, such as purchasing module 103 in FIG. 1, to reference a corresponding number in credit card numbers 702. Public keys 708 are associated with merchant identifiers 706. Each of the public keys 708 is used to encrypt credit card numbers before the numbers are transmitted to the merchant corresponding to one of the merchant identifiers 706.

FIG. 8 shows an example process 800 for enabling a user to make a purchase in a multi-merchant purchasing environment. For example, process 800 may be implemented by a multi-merchant purchasing system to allow a user to purchase downloadable products from multiple merchants with a single transaction. At block 802, the downloadable products for purchasing are identified. The downloadable products may be identified from data provided by one or more catalog providers. At block 804, the user who is purchasing the downloadable products is authenticated. At block 806, updated product information about the downloadable products is obtained from merchants that offer the downloadable products. Further at block 806, a request for extended user data collection may be included. At block 808, the updated product information is provided to the user. At block 809, the extended user data that may have been requested by a merchant at block 806 may be collected. The extended user data may be provided by the user via a user interface or may be retrieved from a data store that contains the information, for example, if the user has already provided the information in an earlier purchase. At block 810, payment information is obtained. The payment information may be provided by the user or may be retrieved from a data store that contains the information, such as if the user has already provided the information in a previous purchase.

At block 812, payment information is provided to each merchant by which the downloadable products to be purchased are offered. Further at block 812, the extended user data collected at block 809 may be provided to each merchant. At block 814, purchasing information from each merchant is received. At block 816, the purchasing information is recorded in a locker associated with the user. At block 818, the user is enabled to download the purchased products.

FIG. 9 shows an example process 900 for enabling a user to download products that are properly purchased. Process 900 may be implemented by a multi-merchant purchasing system to interact with a software assistant in a user's computing device. At block 902, a request to download purchased products for a user is received from a software assistant. The purchased products may be provided by different merchants. The request may be for downloading the purchased products for the first time or for a repeated downloading. At block 904, purchasing information from the user's locker is determined. At decision block 906, a determination is made whether downloading is allowed. The determination may be determined based on the licenses of the purchased products. If downloading is not allowed, process 900 moves to block 912 where the downloading request is denied.

Returning to decision block 906, if downloading is allowed, process 900 moves to block 908 where the user is enabled to download the purchased products. At block 910, the purchasing information is updated to reflect the downloading.

FIG. 10 shows an example process 1000 for downloading a downloadable product purchased through a multi-merchant purchasing system. At block 1002, the purchased product for downloading is identified. At block 1004, a location for downloading the product is obtained from the merchant by which the product is provided. The location typically includes a URL, IP address, or other identifier of a location in a network.

At block 1006, the location is provided to a client that requests the downloading. At block 1008, a hash value derived from the product for downloading is received from the merchant. At block 1010, another hash value calculated by the client is received from the client. At block 1012, a validation is provided to the client if the hash values match.

FIG. 11 shows an example process 1100 for downloading and installing product purchased through a multi-merchant purchasing system. Process 1100 may be implemented by a software assistant. At block 1102, a list of products associated with a locker on the multi-merchant purchasing system. The locker is typically associated with a user. The products may be provided by multiple merchants. At block 1104, downloading locations for the products are determined. Each location corresponds to a service of a merchant that provides at least one of the products. At block 1106, the products are downloaded from the locations. At block 1108, the products are automatically installed on the computing device associated with the user.

For repeated downloading, the steps in blocks 1110 and 1112 may be used to configure the downloaded products. At block 1110, previous configurations associated with the products are identified. At block 1112, the products on the device are configured in accordance with the identified configurations. The steps in blocks 1110 and 1112 may be used to automatically image the computing device with software and data that are purchased from the multi-merchant purchasing system.

FIG. 12 shows an example process 1200 for securely providing payment information to a merchant for purchasing downloadable products through a multi-merchant purchasing system. At block 1202, the process determines to send payment information provided by a user to a merchant. At block 1204, a token associated with the user and a merchant identifier is provided to a credit card quarantine module. At block 1206, credit card number encrypted with a public key associated with the merchant indicated by the merchant identifier is received from the credit card quarantine module. At block 1208, other payment information associated with the user is identified. For example, the other payment information may include a name, address, expiration date, security code, phone number, address, or the like. At block 1210, the encrypted credit card number is sent to the merchant along with the other payment information.

FIG. 13 is a screenshot 1300 of an example user interface provided by a catalog provider for purchasing downloadable products from multiple merchants. As shown in example screenshot 1300, a shopping cart associated with a user is presented. The shopping cart includes downloadable products from two different merchants. The user may proceed to purchase the downloadable product with a multi-merchant purchasing system by activating checkout button 1302.

FIG. 14 is a screenshot 1400 of an example user interface for purchasing products through a multi-merchant purchasing system. As shown in FIG. 14, the products from multiple merchants illustrated in FIG. 13 are listed for the user. The information may include updated information, such as prices, description, or the like, provided by each merchant. An authorization selection area 1403 is provided to show the user that the payment information will be provided to each merchant for processing and to enable the user to provide authorization. In an alternative example, extended user data necessary for keying or creating a software license key, for example, a user's organization may be collected. Further extended user data, for example, as a user's preferences with regard to receiving marketing materials, may be also be collected. The user may provide the necessary authorization in area 1403 and complete the purchase by activating the complete purchase button 1405. Upon activation, the payment information and other transactional information would be provided to each merchant for processing. In an alternative example, activating the complete purchase button 1405 may present the user with a user interface for collecting extended user data as discussed earlier.

FIG. 15 is a screenshot 1500 of an example user interface for managing downloadable products newly purchased through a multi-merchant purchasing system. In area 1502, information about a purchase is presented. As shown in the figure, downloadable products from two different merchants are included in the purchase. In area 1504, the information about the purchased products is shown. The information includes license information associated with the downloadable products. Downloading times are also provided for review by the user. The user may select to start the downloading process by activating a download button 1506. Upon activation, a software assistant may be launched on the user's computing device to perform the downloading.

FIG. 16 is a screenshot 1600 of an example user interface provided by a software assistant for downloading and installing products purchased through a multi-merchant purchasing system. The software assistant is typically a client process executing on the user's computing device. The software assistant typically interacts with the multi-merchant purchasing system to obtain information for downloading and with a merchant service to receive the actual product content. As shown in screenshot 1600, the software assistant may be configured to download multiple products from different merchants at the same time. The software assistant may also be configured to install the downloaded products.

FIG. 17 is a screenshot 1700 of an example user interface provided by a locker of a multi-merchant purchasing system. The locker enables a user associated with the locker to access the downloadable products purchased through the multi-merchant purchasing system. As shown in screenshot 1700, the locker may provide purchase information, such as a list of the purchased products, license information, downloading time, or other information. Depending on the licenses, the locker may also enable to the user to download the purchase products again after the initial download.

FIG. 18 is an example screenshot 1800 of a user interface provided by a multi-merchant purchasing system for a user to review purchases made with the system. As shown in FIG. 18, purchases from multiple merchants may be shown together. Also, links are available for obtaining additional information and support.

FIG. 19 is an example screenshot 1900 of a user interface provided by a multi-merchant purchasing system for a user to manage an account on the system. The user may provide and manage information required for making purchases. When making a purchase with downloadable products from multiple merchants, the provided information is forwarded to each merchant so that the user does not have to go through the purchasing process with each merchant.

FIG. 20 shows example extended user data that may be sent by the merchant 131-133 to the purchasing module 103 in FIG. 1. The purchasing module 103 of FIG. 1 may then collect the information from the user and send the collected information back to the merchant 131-133 of FIG. 1 as part of the transaction. As shown in FIG. 20, the example extended user data may be stored in an extended user data store 2000. Such extended user data may be formatted as extensible markup language (XML) and may conform to an extensible markup language schema such as XML Schema (XSD), XML data type definition (DTD), or the like. The extended user data store may include Name 2010, Label 2020, Required 2030, Canonical Name 2040, and Default Value 2050.

Name 2010 may be a field used to represent the name of the extended data to be collected. Name 2010 may be defined by the merchant 131-133 of FIG. 1 such that the merchant 131-133 of FIG. 1 may identify the information to be collected from the user. As such, Name 2010 may not be presented to the user during the collection of information. Label 2020 may be a field used to represent the text to be presented to the user when the information is collected. In particular, Label 2020 may be used by the purchasing module 103 of FIG. 1 when constructing a user interface to collect the information from the user.

Required 2030 may be a field used to represent whether or not the purchasing module 103 of FIG. 1 is required to collect the information from the user. Required 2030 may be of a Boolean type, binary type, or the like. Canonical Name 2040 may be a field used to refer to the standard type name which may have been previously agreed upon by the merchant 131-133 of FIG. 1 and the purchasing module 103 of FIG. 1. Such a Canonical Name 2040 may be used by purchasing module 103 of FIG. 1 to create a union, minimal set, or intersection of collected information when returning collected information to merchant 131-133 of FIG. 1. For example, two merchants may collect information related to the user's organization and may use the canonical name “organization” to describe the information. The purchasing module 103 of FIG. 1 may then request “organization” information from the user once and may then distribute the organization information to each merchant.

Default Value 2050 may be a field used to store a default value. Such a default value may be provided by the merchant 131-133 of FIG. 1 to the purchasing module 103 of FIG. 1 such that the purchasing module 103 of FIG. 1 may create the user interface created to collect the extended user data and populate the data entry field with the Default Value 2050. Such a Default Value 2050 may allow the purchasing module 103 of FIG. 1 to create the user interface such that the user is not required to enter the information unless they wish to change the Default Value 2050.

FIG. 21 shows an exemplary computer device 2100 for implementing the described systems and methods. In its most basic configuration, computing device 2100 typically includes at least one central processing unit (CPU) 2105 and memory 2110.

Depending on the exact configuration and type of computing device, memory 2110 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. Additionally, computing device 2100 may also have additional features/functionality. For example, computing device 2100 may include multiple CPU's. The described methods may be executed in any manner by any processing unit in computing device 2100. For example, the described process may be executed by both multiple CPU's in parallel.

Computing device 2100 may also include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated in FIG. 21 by storage 2115. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Memory 2110 and storage 2115 are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computing device 2100. Any such computer storage media may be part of computing device 2100.

Computing device 2100 may also contain communications device(s) 2140 that allow the device to communicate with other devices. Communications device(s) 2140 is an example of communication media. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer-readable media as used herein includes both computer storage media and communication media. The described methods may be encoded in any computer-readable media in any form, such as data, computer-executable instructions, and the like.

Computing device 2100 may also have input device(s) 2135 such as keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 2130 such as a display, speakers, printer, etc. may also be included. All these devices are well know in the art and need not be discussed at length.

While the preferred embodiment of the invention has been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the invention. 

1. One or more device-readable media having device-executable instructions for performing actions comprising: identifying a user associated with a commerce application, the commerce application connected through a network with multiple merchants, respective merchants associated with a store separate from others of the multiple merchants; facilitating a user based purchase of at least two products through the commerce application as a single transaction, the at least two products purchased from at least two of the multiple merchants; determining which of the at least two purchased products comprises downloadable products purchased by the user through the commerce application, the downloadable products being purchased from at least two of the multiple merchants; retrieving purchasing information associated with the downloadable products from the at least two multiple merchants, the purchasing information comprising data associated with software activation key licenses associated with the downloadable products; collecting extended user data associated with the user on behalf of at least one of the multiple merchants; providing the extended user data to the at least one of the multiple merchants; and providing the purchasing information to a client application associated with the user.
 2. The one or more device-readable media as recited in claim 1, comprising: receiving a request from the client application to perform an operation comprising downloading a purchased downloadable product; and sending a download link and a hash value to the client application, the download link corresponding to a download location of a merchant associated with the purchased downloadable product.
 3. The one or more device-readable media as recited in claim 2, the requested operation comprising at least one of repeated downloading of the purchased downloadable product, downloading the purchased downloadable product onto multiple computing devices, and upgrading a software activation key license associated with the purchased downloadable product.
 4. The one or more device-readable media as recited in claim 2, comprising updating the purchasing information to comprise the performed operation.
 5. The one or more device-readable media as recited in claim 2, comprising providing information about the performed operation to the merchant associated with the purchased downloadable product corresponding to the operation.
 6. The one or more device-readable media as recited in claim 1, comprising: determining configuration information of purchased products corresponding to a computing device associated with the user; and providing instructions to the client application to automatically image the computing device based, at least in part, on the configuration information.
 7. The one or more device-readable media as recited in claim 1, comprising authenticating the user before providing the purchasing information to the client application.
 8. The one or more device-readable media as recited in claim 1, the extended user data formatted as extensible markup language data.
 9. The one or more device-readable media as recited in claim 1, the extended user data reduced to a smallest set of extended user data before being provided to the at least one of the multiple merchants.
 10. A method in a commerce application comprising: identifying a user in the commerce application; facilitating a user based purchase of at least two products through the commerce application as a single transaction, the at least two products being purchased from at least two different merchants; determining which of the at least two purchased products comprise downloadable products, the downloadable products associated with at least one of the at least two different merchants; retrieving purchasing information associated with the downloadable products, the purchasing information comprising data associated with licenses associated with the downloadable products; collecting extended user data associated with the user on behalf of the at least one merchant associated with the downloadable products; providing the extended user data to the at least one merchant; providing the purchasing information to a client application associated with the user; receiving a request to perform an operation comprising downloading at least one of the purchased downloadable products from the user; downloading at least one purchased downloadable product from the associated merchant when the data associated with a license associated with the purchasing information for the at least one purchased downloadable product permits the download; and updating the purchasing information comprising the data associated with the license to indicate that the at least one purchased downloadable product has been downloaded.
 11. The method of claim 10, comprising: sending a download link and a hash value to the client application, the download link corresponding to a download location of the associated merchant.
 12. The method of claim 10, the requested operation comprising at least one of repeated downloading of the at least one purchased downloadable product, downloading the at least one purchased downloadable product onto multiple computing devices, and upgrading the license associated with at least one the purchased downloadable product.
 13. The method of claim 10, comprising providing information about the downloading of the at least one purchased downloadable product to the associated merchant.
 14. The method of claim 10, comprising: determining configuration information of purchased products corresponding to a computing device associated with the user; and providing instructions to the client application to automatically image the computing device based, at least in part, on the configuration information.
 15. The method of claim 10, comprising authenticating the user before providing the purchasing information to the client application.
 16. The method of claim 10, the extended user data formatted as extensible markup language data.
 17. The method of claim 10, the extended user data reduced to a smallest set of extended user data before being provided to the at least one merchant. 